backend: move the cursor render update on screen changes here

https://bugzilla.gnome.org/show_bug.cgi?id=788860

Gbp-Pq: Name 0010-backend-move-the-cursor-render-update-on-screen-chan.patch

monitor-manager: use g_return_val_if_fail if trying to fetch an invalid monitor

https://bugzilla.gnome.org/show_bug.cgi?id=788860

Gbp-Pq: Name 0009-monitor-manager-use-g_return_val_if_fail-if-trying-t.patch

backends: add 'monitors-updated-internal' signal to only update internal state

Adding an internal signal and use it to update the internal state before
emitting "monitors-changed" which will be repeated by the screen to the world.

https://bugzilla.gnome.org/show_bug.cgi?id=788860

Gbp-Pq: Name 0008-backends-add-monitors-updated-internal-signal-to-onl.patch

settings: Get UI scaling factor from primary logical monitor

Don't use MAX(logical monitor scales) to determine the UI scaling
factor, just use the primary logical monitor. That's where the shell UI
will most likely be.

https://bugzilla.gnome.org/show_bug.cgi?id=788820

Gbp-Pq: Name 0007-settings-Get-UI-scaling-factor-from-primary-logical-.patch

x11-Protect-XChangeProperty-call-with-error-traps

Gbp-Pq: Name 0006-x11-Protect-XChangeProperty-call-with-error-traps.patch

wayland-dma-buf: Don't send modifiers to old clients

The modifier event was only added in v3 of the client; sending it to
older clients (e.g. GStreamer waylandsink) causes them to disconnect
immediately.

Send the older 'format' event to all clients, and only send the newer
'modifier' event to resource versions 3 or above.

https://bugzilla.gnome.org/show_bug.cgi?id=788558

Gbp-Pq: Name 0001-wayland-dma-buf-Don-t-send-modifiers-to-old-clients.patch

skip-failing-tests-325

Gbp-Pq: Name skip-failing-tests-325.patch

skip-failing-tests

Gbp-Pq: Name skip-failing-tests.patch

gtk-shell: Work around non-working startup notifications

GNOME Shell relies on the MetaScreen::startup-sequence-changed signal,
which is tied to (lib)startup-notification and therefore X11. As a result,
when we remove the startup sequence of a wayland client, GNOME Shell will
not be notified about this until startup-notification's timeout is hit.
As a temporary stop-gap, go through XWayland even for wayland clients,
so that the signal is emitted when expected.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=768531
Applied-upstream: no

Gbp-Pq: Name bgo768531_workaround-startup-notifications.patch

mutter (3.26.1-6) unstable; urgency=high

  * debian/control.in: Bump libegl1-mesa-dev to (>= 17) (Closes: #878702)
  * Cherry-pick more fixes from gnome-3-26 branch to fix crashes
    and fix unredirecting full-screen windows:
    - 0012-x11-window-Don-t-manage-InputOnly-windows.patch
    - 0013-compositor-Ignore-offscreen-windows.patch
      (LP: #1725821)
    - 0015-monitor-normal-Prefer-modes-with-same-flags.patch
    - 0016-monitor-unit-tests-Check-non-first-preferred-modes.patch
      (LP: #1725153)
    - 0017-compositor-Avoid-a-crash-if-top-window-finalized.patch
    - 0018-Revert-ClutterActor-Optimize-away-idempotent-scale.patch
    - 0019-Revert-tests-Fix-actor-anchors-test.patch
      (Closes: #788140)
  * Set urgency to high to not further delay the gjs/mutter transition

[dgit import unpatched mutter 3.26.1-6]

Import mutter_3.26.1-6.debian.tar.xz

[dgit import tarball mutter 3.26.1-6 mutter_3.26.1-6.debian.tar.xz]

Import mutter_3.26.1.orig.tar.xz

[dgit import orig mutter_3.26.1.orig.tar.xz]